Overview | License | Training | Support
Release Notes for the Intel® Managed Objects ToolKit
Release Software Version 1.0
August 23, 1997
This file includes updated information for the documentation provided with the Intel Managed Objects ToolKit Release Version 1.0. The information in this file supercedes that in the online help or other documentation.
CONTENTS
- Technical Support Procedures
- General Information
- Known Anomalies
PART 1: TECHNICAL SUPPORT PROCEDURES
Intel Managed Objects ToolKit support contact information
FAQs and Newsgroups are available from the home page for the product found in the Developer area of:
http://www.intel.com/ManagedPC
Email
Phone: (800) 628-8686
The Desktop Management Task Force, Inc. (DMTF) provides documents, files and support through their World Wide Web home page. As the Desktop Management Interface (DMI) technology grows and develops, announcements and updates are distributed through these points of contact.
World Wide Web site: http://www.dmtf.org
Internet FTP site: ftp.dmtf.org
Free electronic copies of the DMI Specification and updated reference MIF files containing the latest revisions of DMTF-approved Standard Groups may also be obtained.
This information was current and correct at the time this product was
released.
PART 2: GENERAL INFORMATION
DMI 2.0 Support
This product directly supports all functionality provided by the DMI 2.0 Service Provider.
This Released Version 1.0 of the Intel Managed Objects ToolKit software enables users to quickly create Desktop management applications and tools using Visual Basic* 5.0, Microsoft Word* 7.0, and other OLE2.0 enabled tools.
Visual Basic 5.0 Browser Example
A Visual Basic 5.0 DMI Browser example application with source is provided for users to explore the use of the DMI Engine control's methods and properties. The example files are commented so a user can quickly learn the capabilities provided by the ToolKit.
Visual Basic 5.0 MOTQueryTool Control Example
A Visual Basic 5.0 sample application with source which demonstrates the use of the Query Engine and Query Tool controls is available. The example files are commented so that a user can quickly learn the capabilities provided by the ToolKit.
C++ MOTDmiEngine Control Example
A simple C++ console application with source which demonstrates the use of the DMI Engine via its C++ interfaces. The example files are commented so a new user can quickly learn the capabilities provided by the ToolKit.
Context Sensitive help
An important part of the Intel Managed Objects ToolKit, context sensitive help, is available for all of the ToolKit's controls. Also included is a general DMI 2.0 help tutorial.
Type library files included for all controls.
Type library files (.ODL ) and the necessary header files are included under the \BIN directory for creating headers for C++ developers.
This document provides late-breaking information on the Managed Objects
ToolKit. When available, You will be able to download updated versions of
the Managed Objects Toolkit from the developer area Intel Web site at http://www.intel.com/managedpc.
PART 3: KNOWN ANOMALIES
Microsoft Ships COMCTL32.OCX file in MS CCE (Control Creation Edition) that is incompatible with shipping VB5.0.
The Microsoft CCE tool, which is downloadable from Internet, contains a control
COMCTL32.OCX which is incompatible with the currently shipping Visual Basic 5.0 release.
The version of the offending control, which is viewable using Windows Explorer, is 500.3828.
The correct version shipped with VB5.0 is 5.00.3714. If you have installed Microsoft's CCE you
must unregister and delete the control manually. The Intel Managed Objects ToolKit installation
program will then copy and register the correct version of the control.
DMIEngine control
- Termination of a remote connection during processing of an asynchronous event will cause an automation exception error to be fired upon access of the DMIEvent object.
- Add/Delete Language notifications are currently not supported in this release.
- To access or remove a row in a collection using a key list, each DMIAttribute object in the keylist must minimally contain a value and an valid id.
- The Parent property for all objects has been removed.
- Add Notifications.
- On receiving group add notifications, the control will erratically return
the incorrect notification type.
- Incorrect notification description randomly occurs for connected groups.
- DMIMgmtNodes Collections
- Removal of a node with an invalid index parameter successfully decrements
the count.
- Setting NetworkAddress, RPC, or Transport should throw Read-Only
exceptions, but does not.
- Adding an unconnected DMIMgmtNode to a DMIMgmtNodes collection is illegal
and should raise an exception. Currently it does not.
- Supplying a path to a DMIMgmtNodes collection for item that does not
exist returns the first item in the collection.
- DMIGroups
Adding unconnected group does not throw an ACCESS_DENIED exception.
- The count property in DMIGroups collections can become unsynchronized w/ the SP when the RemoveAll method is invoked.
- The following errors may occur when accessing methods and properties through the IDispatch interface.
- Unable to create objects for DMIEvents, and DMINotification
- Invalid procedure call or arg. adding components.
- Type mismatch error removing languages.
- Automation error adding group mif.
- Automation error adding rows.
- Automation error reading files.
- Pragma property is not implemented in this version.
Query Engine control
The Query Engine visible property is TRUE at runtime by default. Developer should set this property to FALSE at runtime.
Query Tool control
Runtime
No known issues.
Design Time
The GUID for the MOTQueryTool ActiveX control has changed from the Beta 1 Preview Release.
Existing projects which use Beta 1 will not work with this release. Unregister the Beta 1 MOTQueryTool before installing this release. (Uninstalling the Beta 1 toolkit will do this for you.) If you have existing code which uses Beta 1, then perform these steps to integrate the new control:
- Unregister the Beta 1 MOTQueryTool.ocx.
- Open your project. Ignore Query Tool load errors.
- Open any form with the Query Tool control on it and delete the control (note the name of your control).
- Add the Beta 2 MOT Query Tool to the components used by your project.
- Drag the control back on to your form.
- Change the control name to your old name.
Hyper Text Markup (HTM) pages which use the control can be easily updated by replacing your existing GUID with the one listed below:
7C639641-DDCB-11D0-9671-00AA003B1305
Management Directory control
The control requires unique names Group or Machine items within a Group.
Visual Basic 5.0 Browser Example
- Local network access does not work.
- Display of group table objects with zero rows causes application fault.
* Legal Information © 1998 Intel Corporation
|